…ng loop

Add a parallel `spec-sync-v2` job that mirrors the proven V1 loop, pointed at the
V2 spec on the AIDE gateway (aide.staging.landing.ai/openapi.json) and a separate
`spec-sync/v2` branch, with a V2-tailored wiring prompt. Reuses the existing
check-drift / fetch-normalize / gen-models scripts unchanged; the V1 job is
untouched.

The committed baseline `specs/v2-aide.json` is the FULL current spec, so
check-drift reports no drift and the loop ships live but quiet — it fires only on a
future real V2 spec change. /v2/workflow is intentionally deferred (not shipping
yet): it stays in the baseline (so it isn't flagged as drift) and the AI-wiring
prompt explicitly excludes the three /v2/workflow* routes so a future unrelated
drift can't pull them in.

Hosts (do not conflate): V2 spec = aide.[env]; V2 API = api.ade.[env]. The V2
contract tests from #109 gate the spec-sync/v2 branch as the live guardrail.

Design: docs/design/v2-spec-sync-extension.md.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

…ant AI-wiring) (#110)

* feat(spec-sync): track V2 spec drift (AIDE gateway) + dormant AI-wiring loop

Add a parallel `spec-sync-v2` job that mirrors the proven V1 loop, pointed at the
V2 spec on the AIDE gateway (aide.staging.landing.ai/openapi.json) and a separate
`spec-sync/v2` branch, with a V2-tailored wiring prompt. Reuses the existing
check-drift / fetch-normalize / gen-models scripts unchanged; the V1 job is
untouched.

The committed baseline `specs/v2-aide.json` is the FULL current spec, so
check-drift reports no drift and the loop ships live but quiet — it fires only on a
future real V2 spec change. /v2/workflow is intentionally deferred (not shipping
yet): it stays in the baseline (so it isn't flagged as drift) and the AI-wiring
prompt explicitly excludes the three /v2/workflow* routes so a future unrelated
drift can't pull them in.

Hosts (do not conflate): V2 spec = aide.[env]; V2 API = api.ade.[env]. The V2
contract tests from #109 gate the spec-sync/v2 branch as the live guardrail.

Design: docs/design/v2-spec-sync-extension.md.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

* fix(spec-sync): address Copilot review on the V2 loop

- Security: drop rye/scripts shell from the AI step's allowedTools (only
  Edit/Write/Read/Glob/Grep/git-diff) so a prompt-injected spec can't execute
  code with the push PAT; add a fixed step that discards any agent edit to
  scripts/.github/specs before running the trusted ./scripts/format.
- Broaden the wiring prompt to cover every changed operation backing client.v2
  (field changes on existing ops + /v1/files, not only new /v2 routes).
- Permit backward-compatible signature additions (new optional kwargs); verified
  surface-lock does not flag an added optional parameter.
- Docs: resources/v2/__init__.py stays unchanged (no sub-resource re-export);
  genericize the Phase-2 design away from the deferred workflow feature.

Follow-up (V1 + V2): persist-credentials:false + read-only action token.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

* fix(spec-sync): harden V2 loop per second Copilot round

- Sanitizer: enforce a product-code ALLOWLIST (src/tests/docs/api.md) instead of
  a 3-dir deny-list, before format AND staging. A repo-wide agent Write to e.g.
  pyproject.toml (which defines `rye run format`) can no longer execute in the
  trusted format step or reach the commit via `git add -A`. Verified in a scratch
  repo: out-of-scope tracked edits reverted, untracked injections deleted,
  legitimate src/tests/docs additions kept.
- Open-PR check: fail CLOSED — capture `gh pr list` result outside the `if`
  condition so a transient API/auth failure aborts instead of silently becoming
  open=false and force-pushing over an existing reviewed PR branch.
- PR body: mark the AI commit conditional (workflow-only drift / AI no-op produces
  a mechanical-only PR), so mechanical-only PRs don't carry an inaccurate summary.

Co-Authored-By: Claude Opus 4.8 <[email protected]>

* fix(spec-sync): wire component-only V2 drift (response-model fields)

Broaden the AI-wiring prompt to inspect changed components.schemas, not just
operation/path hunks: a response-field addition changes only a component (e.g.
ParseResponse) and its generated model, not the operation. Instruct the agent to
trace $ref consumers of changed schemas to non-workflow operations, and to
distinguish request fields (new optional method param) from response-model fields
(add to the response type under types/v2/).

Co-Authored-By: Claude Opus 4.8 <[email protected]>

---------

Co-authored-by: Claude Opus 4.8 <[email protected]>